Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

please update install instructions - fail #2954

Closed
john-clark opened this issue Apr 30, 2013 · 6 comments
Closed

please update install instructions - fail #2954

john-clark opened this issue Apr 30, 2013 · 6 comments
Labels
>enhancement v0.90.8 v1.0.0.RC1

Comments

@john-clark
Copy link

Incomplete information on to make this software.

Please update the instructions on how to complete this process manually

/usr/local/src # git clone git://github.com/elasticsearch/elasticsearch.git
/usr/local/src # cd elasticsearch/
/usr/local/src/elasticsearch # bin/elasticsearch -f
bin/elasticsearch.in.sh: line 3: $ES_CLASSPATH:$ES_HOME/lib/${project.build.finalName}.jar:$ES_HOME/lib/:$ES_HOME/lib/sigar/: bad substitution
You must set the ES_CLASSPATH var
@dadoonet
Copy link
Member

Where did you get theses instructions?

@s1monw
Copy link
Contributor

s1monw commented Apr 30, 2013

please download an official release or use the package that is produced from mvn package (in target/release) the instructions you got are wrong.

@s1monw s1monw closed this as completed Apr 30, 2013
@dadoonet
Copy link
Member

Yes. Official documentation is here: http://www.elasticsearch.org/overview/#installation

@john-clark
Copy link
Author

nice support...rm -rf elastics*

if you ever decide to document your project I may look at it again. probably not.

tip: make instructions are typically put in the readme for us old timers

@kimchy
Copy link
Member

kimchy commented Apr 30, 2013

@john-clark unsure where you are coming from, read the README: https://github.com/elasticsearch/elasticsearch/blob/master/README.textile, it mentions downloading ES and then running it using bin/elasticsearch, or, if you head all the way to the bottom, talks about building it from source.

@s1monw
Copy link
Contributor

s1monw commented Apr 30, 2013

if you want to build from the source you should build a release with mvn package that is pretty standard and I am happy to help. Yet, this is an issue and not a support list so you should get pretty descent support there. If you want to get started with ES there is a pretty good link that is straight forward (http://www.elasticsearch.org/guide/reference/setup/) I am all sorry if that came across as a complaint or anything, I was just making sure that this is the wrong path and you might wanna start from a pre-build package.

ongardie added a commit to ongardie/elasticsearch that referenced this issue Dec 11, 2013
@ongardie
Print nice error in bin/elasticsearch if user needs to run Maven
7adce4d 
Before, people that cloned the repo and expected to be able to run
bin/elasticsearch would be met with an awful shell error: the shell
interprets Maven variables like ${project.build.finalName} as shell
variables yet can't handle names of the form ${x.y}. This commit
explicitly checks to make sure that Maven has done its substitutions
before continuing; if Maven hasn't been run, it gives a helpful error
message.

Fixes elastic#2954.
@ongardie ongardie mentioned this issue Dec 11, 2013
Closed
spinscale pushed a commit that referenced this issue Dec 13, 2013
@ongardie @spinscale
Print nice error in bin/elasticsearch if user needs to run maven
a4814c2 
Before, people that cloned the repo and expected to be able to run
bin/elasticsearch would be met with an awful shell error: the shell
interprets Maven variables like ${project.build.finalName} as shell
variables yet can't handle names of the form ${x.y}. This commit
explicitly checks to make sure that Maven has done its substitutions
before continuing; if Maven hasn't been run, it gives a helpful error
message.

Fixes #2954.
spinscale pushed a commit that referenced this issue Dec 13, 2013
@ongardie @spinscale
Print nice error in bin/elasticsearch if user needs to run maven
c195ed8 
Before, people that cloned the repo and expected to be able to run
bin/elasticsearch would be met with an awful shell error: the shell
interprets Maven variables like ${project.build.finalName} as shell
variables yet can't handle names of the form ${x.y}. This commit
explicitly checks to make sure that Maven has done its substitutions
before continuing; if Maven hasn't been run, it gives a helpful error
message.

Fixes #2954.
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@ongardie @spinscale
Print nice error in bin/elasticsearch if user needs to run maven
38870a5 
Before, people that cloned the repo and expected to be able to run
bin/elasticsearch would be met with an awful shell error: the shell
interprets Maven variables like ${project.build.finalName} as shell
variables yet can't handle names of the form ${x.y}. This commit
explicitly checks to make sure that Maven has done its substitutions
before continuing; if Maven hasn't been run, it gives a helpful error
message.

Fixes elastic#2954.
@jasontedor jasontedor mentioned this issue Jul 30, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.90.8 v1.0.0.RC1
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Print nice error in bin/elasticsearch if user needs to run Maven ongardie/elasticsearch
4 participants
@kimchy @dadoonet @s1monw @john-clark